Release 10.1A: OpenEdge Development:
Progress Dynamics Repository Reference

gsm_session_type table — gsmse

The gsc_session_type table is the central table of the Session and Configuration group. This table maintains the list of supported session types. This table also holds parameter details for the session, such as whether to support failover and inactivity timeouts for sessions.

Table 13–1 lists the table’s FLA, fields, and foreign keys.

Table 13–1: gsm_session_type table information 

Table FLA	Fields (data type)	Foreign keys
gsmse	session_type_obj (Decimal) session_type_code (Character) session_type_description (Character) physical_session_list (Character) valid_os_list (Character) inactivity_timeout_period (Decimal) automatic_reconnect (Logical) extends_session_type_obj (Decimal)	session_type_obj

Table 13–2 gives details of the table’s indexes.

Table 13–2: gsm_session_type index information 

Index name	Elements	Type
XPKgsm_session_type	session_type_obj	Primary Unique
XAK1gsm_session_type	session_type_code	Unique
XIE1gsm_session_type	session_type_description	Nonunique
XIE2gsm_session_type	extends_session_type_obj	Nonunique

A session type is a namespace for grouping specific types of sessions together. For example, some session types might be a “receipting workstation” and a “salesman’s Web agent.”

Each session type is combined with a physical session type that maps to a list of known Progress 4GL run-time environments. Thus, “receipting workstation” might map to a 4GL GUI client, and “salesman’s Web agent” might map to a WebSpeed® Transaction Agent. You can create any number of session types, mapping them to specific 4GL session types.

Where different managers must be prestarted for different applications, the different applications are defined as new session types.

To run locally without OpenEdge AppServer™ connections, you would define a new session type that connects to appropriate databases and has no session service records for the AppServer logical services. That would force them to not connect, using the session handle for code portability instead. This new session type would define a different set of managers to run as well. It would run the server-side managers locally.

There is a recursive join to the gsc_session_type table to support inheritance of settings across multiple session types. This makes the modification, reuse, and creation of session types easier. The program that generates the icfconfig.xml file reads the extra details from the linked session types and writes out an accumulated set of configuration details.